unchecked exception造句

• To convert the exceptions into meaningful unchecked exceptions
  ）将异常转换为有意义的（ unchecked ）异常。
• It does not guard against the plug - in throwing any unchecked exceptions
  它并不防备抛出任何未查出异常的插件。
• With unchecked exceptions , we don t have that crutch to lean on
  对于非检查型异常，我们则没有这个支撑可以依靠。
• When using unchecked exceptions , also remember that you may need to use
  使用非检查型异常时还要记住，即使您并不捕获任何异常，也可能需要使用
• Unlike c , though , the java language supports both checked and unchecked exceptions
  但是，与c + +不一样的是， java语言支持检查型和非检查型异常。
• In this article , brian goetz looks at the pros and cons of using unchecked exceptions
  在本文中， brian goetz考察了关于使用非检查型异常的优缺点。
• From " the java tutorial " outlines the official position on checked versus unchecked exceptions
  的一节中列举了关于检查型以及非检查型异常的官方立场。
• Johnson suggests making the decision between checked and unchecked exceptions on a package - by - package basis
  Johnson建议在每个包的基础上选择检查型和非检查型异常。
• In a similar scenario , you might run across an application throwing an unchecked exception say , a subclass of
  在类似的场景中，您可能遇到应用程序抛出未检查的异常（比如像
• Another way that listeners can make trouble for unwary event sources is throwing an unchecked exception
  对于不小心的事件源，侦听器会造成麻烦的另一个方式是：抛出未检测的异常。
• The decision to use unchecked exceptions is a complicated one , and it s clear that there s no obvious answer
  关于是否使用非检查型异常的决定是复杂的，并且很显然没有明显的答案。
• While most of the time , we never intend to throw unchecked exceptions , it does sometimes happen anyway
  虽然大多数时候，我们不会故意抛出未检测异常，但是确实有些时候会发生这种情况。
• I don t see any reason why this problem wouldn t be equally common with java class libraries that rely heavily on unchecked exceptions
  我看不出有任何理由可以说该问题对于java类库不是同样的常见，因为jav类库严重依赖于非检查型异常。
• Recently , several prominent writers have started to come to the position that unchecked exceptions may have more of a place in good java class design than previously thought
  最近，几位著名的作者已经开始认为非检查型异常在优秀的java类设计中有着比以前所认为的更为重要的地位。
• If you do decide to use unchecked exceptions , you need to document this choice thoroughly , including documenting in javadoc all the unchecked exceptions a method might throw
  如果决定使用非检查型异常，您需要彻底地文档化这个选择，包括在javadoc中文档化一个方法可能抛出的所有非检查型异常。
• Rather than make the rest of the jdo - consuming classes pay for this possibility in the form of catching and rethrowing these exceptions , he suggests using unchecked exceptions here instead
  他建议在这里使用非检查型异常，而不是让其余的使用jdo的类通过捕获和重新抛出这些异常的形式来弥补这个可能性。
• However , in multithreaded applications , threads can die silently due to unchecked exceptions - leaving users and developers scratching their heads as to what happened and why
  但是，在多线程应用程序中，由于未查出的异常，线程会无声无息地死亡使得用户和开发人员对于发生的问题和为什么发生这些问题毫无头绪。
• Josh bloch offers the following bits of wisdom regarding checked and unchecked exceptions , which are consistent with but not quite as strict as what " the java tutorial " suggests
  ） ， josh bloch提供了下列关于检查型和非检查型异常的知识点，这些与“ the java tutorial ”中的建议相一致（但是并不完全严格一致） ：
• Johnson also enumerates a middle ground , for which he asks the question , " will only a minority of callers want to handle the problem ? " for these scenarios , he also suggests using unchecked exceptions
  Johnson还列举了一个中间情形，对此他提出一个问题， “只是少数调用者希望处理问题吗？ ”对于这些情形，他也建议使用非检查型异常。
• Having used exceptions in c , where all exceptions are unchecked , i have found that one of the biggest risks of unchecked exceptions is that they are not self - documenting in the way checked exceptions are
  通过在c + +中使用异常，其中所有的异常都是非检查型的，我已经发现非检查型异常的最大风险之一就是它并没有按照检查型异常采用的方式那样自我文档化。